McGraw-Hill's GMAT, 2014 Edition by James Hasik

McGraw-Hill's GMAT, 2014 Edition by James Hasik

Author:James Hasik
Language: eng
Format: epub
Publisher: McGraw-Hill Education
Published: 2013-01-15T00:00:00+00:00


Situation. Did you set up the situation or problem quickly and cleanly? Might the listener be bored before you get to the point? Did you use industry-specific geek talk that he couldn’t possibly understand? Above all, keep the setup short and strip the story down to the essential point. Eliminate detail.

Task. Did you specify the challenge, job, or project that you faced? Was it obvious, or did you have to work to identify the hidden task that really needed to be taken on? Was it the sort of thing that only a select group of people could handle?

Action. Did you clarify your role in the job or project? Did you specify the action you took? Why it was important? What would have happened had no one acted?

Result. Did you get to a result or describe the outcome? What did you learn from the results? Are your actions still having some effect? Have you repeated this experience since then? As with all things MBA, try to quantify the results.

For each story that you plan to relate, strive to

Make a purposeful transition from situation and task to action and result. There is an art to these stories, and while the concept may seem affected and artificial, skill in relating accomplishments this way will help you, whether you are applying to graduate school, trying to land that job at Booz Allen, or angling to convince a venture capitalist that you’re the one to entrust with her next $10 million. Thus, your stories must be well scripted without seeming scripted. In the end, you just need to know your own career and experience very, very well.

Create a balance between “we” and “I.” That said, it’s not just about you. The stories you relate about yourself should walk a fine line between extolling your virtues and demonstrating your humility. Talk too much about yourself, and you’ll come off as “not a team player.” Talk too much about the team, and you’ll appear to be a straphanger—just one more warm body loaded in the back of the airplane on the way to the target. See the difference?

Tell the story from the point of view of that functional area. No experience in the software business? No problem, as long as your story plausibly relates to the issue at hand. Remember, the people to whom you’re trying to sell your experience really don’t care about your experience. They care about what you can do for them with that experience.

Tell a story they’d want to hear about. Since they don’t care, and they’re going to need to listen to hundreds of these spiels over merlot and cheese squares, try to be engaging. Your story just might be the one that sticks out and saves the evening.



Download



Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.